Efficient management and configuration of in-band resources

ABSTRACT

There is disclosed herein, by way of example, an enterprise server computing platform configured to provide stateless computing, wherein each node has no set configuration, including for example, MAC addresses, UUIDs, firmware, and BIOS by way of non-limiting example. Certain devices or peripherals may be considered “out-of-band,” meaning that they are discoverable and configurable in standby power by a baseboard management controller (BMC) without need for an OS. Certain other peripherals are considered “in-band,” meaning that they may need an OS for discovery and configuration. According to one or more example embodiments of this Specification, a system and method are disclosed for automatically discovering and configuring out-of-band devices on a server. Out-of-band devices may then be disabled, and the server is booted with minimal resources and a bootstrap OS to discover and configure in-band devices.

FIELD OF THE DISCLOSURE

This application relates to the field of virtual computing, and moreparticularly to a system and method for efficient management andconfiguration of in-band resources.

BACKGROUND

The unified computing system (UCS) is an x86-based data center platformuseful for providing, for example, large-scale data and hostingservices. In certain embodiments, a UCS may include one or more bladeservers, one or more rack servers, or a combination of blade and rackservers. Both the rack form factor and the blade form factor provideindustry-standard connectors and interfaces, enabling a UCS to conformto open protocols and to use third-party hardware and software. Incertain embodiments, a UCS may be provided with a plurality of servers,each of which may host a hypervisor such as a VMware ESX, ESXi, aMicrosoft Hyper-V, a Citrix Zen server, or similar. In otherembodiments, a server may be provided with a host operating system (OS),and may provide other virtual machines, such as a VMware workstation.

It will be recognized that in accordance with industry practice, ahypervisor may be provided in one of at least two configurations. A typeI hypervisor runs directly on a server's hardware, and manages guest OSsdirectly without the need of a host OS.

Examples of type I hypervisor's include the aforementioned VMware ESXand ESXi, Microsoft Hyper-V, and Citrix XenServer.

A type II hypervisor includes a host OS running on the hardware, whichthen provides hypervisor management software. Examples of type IIhypervisors include VMware workstation and virtual box hypervisors. Itis also possible to provide certain hybrid hypervisor that are notstrictly type I or type II, for example, a kernel-based virtual machine(KVM).

In certain circumstances, it is desirable for a server providinghypervisor functionality to have certain configurable resources ratherthan fixed and immutable attributes. Thus, one useful function of a UCSis to provide configurable attributes for servers, and thus provideincreased flexibility to clients operating hypervisors on the UCS.

Because UCS is an open architecture, it may be compatible withoff-the-shelf and legacy solutions. Available resources on a server maybe usefully divided into two categories. Out-of-band resources aredirectly configurable by the UCS, without the need for a host OS runningon the server. In-band resources are resources that, for example, maynot be UCS-aware because they are legacy or off-the-shelf solutions, andtherefore are not directly configurable by an out-of-band management. Inthat case, in-band resources may need to be configured by an OS.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is best understood from the following detaileddescription when read with the accompanying FIGURES. It is emphasizedthat, in accordance with the standard practice in the industry, variousfeatures are not drawn to scale and are used for illustration purposesonly. In fact, the dimensions of the various features may be arbitrarilyincreased or reduced for clarity of discussion.

FIG. 1 is a block diagram of a UCS according to one or more examples ofthe present Specification.

FIG. 2 is a block diagram of a BMC interacting with subsystems accordingto one or more examples of the present Specification.

FIG. 3 is a block diagram of a BMC according to one or more examples ofthe present Specification.

FIG. 4 is a flow chart of a method according to one or more examples ofthe present Specification.

FIG. 5 is a flow chart of a method according to one or more examples ofthe present Specification.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Overview

There is disclosed herein, by way of example, an enterprise servercomputing platform such as Cisco's® Unified Computing System (UCS),configured to provide stateless computing, wherein each node has no setconfiguration, including for example, media access control (MAC)addresses, universally-unique identifiers (UUIDs), firmware, and basicinput/output system (BIOS) settings by way of non-limiting example.Certain devices or peripherals may be considered “out-of-band,” meaningthat they are discoverable and configurable in standby power by abaseboard management controller (BMC) without need for an OS. Certainother peripherals are considered “in-band,” meaning that they may needan OS for discovery and configuration. According to one or more exampleembodiments of this Specification, a system and method are disclosed forautomatically discovering and configuring out-of-band devices on aserver. Out-of-band devices may then be disabled, and the server isbooted with minimal resources and a bootstrap OS to discover andconfigure in-band devices.

EXAMPLE EMBODIMENTS OF THE DISCLOSURE

The following disclosure provides many different embodiments, orexamples, for implementing different features of the present disclosure.Specific examples of components and arrangements are described below tosimplify the present disclosure. These are, of course, merely examplesand are not intended to be limiting. Further, the present disclosure mayrepeat reference numerals and/or letters in the various examples. Thisrepetition is for the purpose of simplicity and clarity and does not initself dictate a relationship between the various embodiments and/orconfigurations discussed.

Different embodiment may have different advantages, and no particularadvantage is necessarily required of any embodiment.

An important benefit of UCS as disclosed in this Specification isso-called “stateless computing.” Stateless computing means that eachnode within the UCS, such as a server, need not have a fixed orimmutable configuration. Rather, many attributes of the node can bepersistently configured, and the node can then be operated as thoughthose persistent attributes were immutable attributes of a standalonesystem. For example, a standalone system may have a fixed and immutablemedia access control (MAC) address for a network interface card (NIC).The MAC address may be, for example, provided by a read-only memory(ROM) or other memory that is not user configurable. In contrast, a nodeon a UCS may have a user configurable MAC address. Thus, a UCS clientcan specify a desired MAC address, and the NIC on that UCS node may beconfigured with that MAC address.

If the NIC is specifically designed to be UCS-capable and aware, thenconfiguration of the NIC may be accomplished by out-of-band management.This means that a UCS manager device (UCSM) may access a baseboardmanagement controller (BMC) resident on the node, and the BMC mayautonomously configure the NIC with the desired MAC address. On theother hand, if the NIC is an off-the-shelf or legacy NIC that is notUCS-aware and capable, configuration of the MAC address may not beaccomplished via the BMC or out-of-band management. In that case, an OSrunning on the UCS node may be required to configure a desired MACaddress on the NIC. This situation is referred to as in-band management.

Nonlimiting examples of attributes that may be configured by a UCS,either in-band or out-of-band, include the following: For storagedevices, worldwide port name (WWPN) or worldwide node name (WWNN) of theserver computer, virtual storage area networks (VSANs) with which theserver computer is associated, any adapter policy specifying errorhandling and timing settings, and configurations of the local storagedrive of the server computer.

Configurable hardware attributes may include, by way of nonlimitingexample, a universally unique identifier (UUID) of the server computer,basic input/output system (BIOS) settings, firmware levels/versions ofthe server computer, and boot policies.

Network attributes that may be configurable include, by way ofnonlimiting example, the MAC address of the server computer, the NICfirmware (e.g., associated with the network interface) of the servercomputer, the quality of service (QoS) assigned to the server computer,and the virtual local area networks (VLANs) switch to which the servercomputer is assigned or associated.

Operational attributes that may be configurable include, by way ofnonlimiting example, data indicating external management access,firmware bundles and management of the server computer, health policy ofthe server computer, and an activation attribute that indicates whetherthe service profile is active or inactive.

FIG. 1 is a block diagram of UCS 100 according to one or more examplesof the present Specification. In an example, UCS 100 includes anenclosure 108, a fabric interconnect 140, and a plurality of cloudservices including a storage area network (SAN) 180, a local areanetwork 182, and management services 184.

Enclosure 108 may be configured as a rackmount system, a blade system,or any other suitable enclosure type. To facilitate discussion,enclosure 108 will be treated herein as a blade chassis. Enclosure 108may include a number of slots to receive UCS nodes such as servers 110.It should be noted that a server is not the only type of possible UCSnode, and that other types of UCS nodes are available. For example,certain UCS nodes may be provisioned for use as storage appliances,security appliances, or other useful types of appliances.

In this example, enclosure 108 includes two servers 110. Specifically,server 110-1 is a full-slot server, while server 110-2 is a half-slotserver. It should be recognized that many other types of servers arepossible, and that in certain embodiments, not all servers 110 need tobe necessarily provided with an enclosure 108. In some embodiments, aserver 110 may be a standalone device that is communicatively coupled toenclosure 108 or to fabric interconnect 140. It should also be notedthat various types of interconnections and buses will be disclosedwithin this Specification. As used throughout this Specification, a“bus” or “interconnect” includes any wired or wireless interconnectionline, network, connection, bundle, single bus, multiple buses, crossbarnetwork, single-stage network, multistage network or other conductionmedium operable to carry data between parts of a computing device, orbetween computing devices. It should be noted that these uses aredisclosed by way of non-limiting example only, and that some embodimentsmay omit one or more of the foregoing buses, while others may employadditional or different buses.

Full-slot server 110-1 includes two NIC adapters 170, specificallyadapter 170-1 and adapter 170-2. NIC adapters 170 are provided tocommunicatively couple full-slot server 110-1 to other network elements.Half-slot server 110-2 may include an adapter 170-3.

Full-slot server 110-1 also includes a BMC 160-1. BMC 160-1 is providedto perform management and configuration functions, especially forout-of-band management operation. It should be noted that BMC 160 isdisclosed by way of a specific example, and that certain BMCs 160provide management and configuration services that are specific to aCisco® implementation of UCS. It is not intended, however, that BMC 160is restricted specifically to the Cisco® BMC. Rather, BMC 160 mayinclude any hardware, software, firmware, or combination thereofconfigured to provide configuration and management services of UCSresources and without the need of a dedicated OS or other similarresident program.

In particular, it is intended that BMC 160-1 perform configuration andmanagement services while server 110 is in a low-power state, such as astandby state. In contrast, OS 130, or bootstrap OS 136 may requirefull-slot server 110 to be in a relatively high power state. It shouldalso be noted that “low-power” and “high-power” are provided simply asrelative terms to one another. In general, a low-power state may includea state where server 110 is not completely powered on and does notprovide all or substantially all of its full functionality, whereas thehigh-power state is a state where server 110 is powered on and providesall or substantially all of its capabilities, less capabilities that arespecifically disabled for purposes of management and configuration asdisclosed herein.

Full-slot server 110-1 also includes a processor 102-1 that isconfigured to communicatively couple to other system elements via one ormore interconnects or buses. Processor 102-1 includes any combination ofhardware, software, or firmware providing programmable logic, includingby way of non-limiting example a microprocessor, DSP, FPGA, PLA, ASIC,or virtual machine processor.

Processor 102-1 is communicatively coupled to a memory 120-1, forexample in a direct-memory access (DMA) configuration. Memory 120 isdisclosed as a single logical block in this example, and may include anysuitable volatile or non-volatile memory technology, including DDR RAM,SRAM, DRAM, flash, ROM, optical media, virtual memory regions, magneticor tape memory, or any other suitable technology. In certainembodiments, memory 120 may be a relatively low-latency volatile mainmemory. It should also be noted that although DMA is disclosed by way ofnon-limiting example, DMA is not the only protocol consistent with thisSpecification, and that other memory architectures are available.

It should be noted that full-slot server 110-1 may also include aseparate storage, such as a hard drive, optical media, or similar,separate from memory 120-1. For simplicity of discussion, memory 120-1and storage are not shown as separate logical blocks in thisconfiguration.

Memory 120-1 may be operable to load and execute both an OS 130-1 and abootstrap OS 136-1. In certain embodiments, OS 130-1 and bootstrap OS136-1 may not be configured to execute concurrently. Rather, bootstrapOS 136-1 may be configured to provide discovery, management, andconfiguration of resources, and in particular in-band resources, asdisclosed herein. OS 130-1, in contrast, may be configured to providemore traditional OS services, and may be configured to take advantage ofthe full capability of full-slot server 110-1.

Full-slot server 110-1 may include both in-band resources 134-1 andout-of-band resources 132-1. Out-of-band resources 132 include thoseresources that are UCS-aware, or that are otherwise configurable withoutthe need for bootstrap OS 136. Thus, UCS 100 can configure out-of-bandresources 132-1, including the attributes described herein that may bedesirably configured on behalf of an end user, without having to operatefull-slot server 110-1 in a higher power configuration. Rather,out-of-band resources 132-1 may be discovered and persistentlyconfigured while keeping full-slot server 110-1 in a low-power mode,such as a standby mode.

Enclosure 108 may also include a half-slot server 110-2. It will berecognized that half-slot server 110-2 is in many respects similar tofull-slot server 110-1, including the provision of a BMC 160-2,processor 102-2, memory 120-2, OS 130-2, bootstrap OS 136-2, in-bandresources 134-2, and out-of-band resources 132-2. However, half-slotserver 110-2 may include fewer overall resources then full-slot server110-1. In particular, in some embodiments, half-slot server 110-2 mayinclude fewer processors and fewer DIMMs, thus providing less processingpower and memory.

Full-slot server 110-1 and half-slot server 110-2 are provided by way ofexample only. It is not intended to imply herein that enclosure 108 isrequired to have at least one full-slot server 110-1 or at least onehalf-slot server 110-2. Furthermore, enclosure 108 may includeadditional servers 110, which may be of any species. Thus, it should beappreciated that enclosure 108 may include a plurality of differenttypes of UCS nodes in many different configurations.

It will also be recognized that enclosure 108 may also include blades orslots that are not servers 110 and that are not UCS specific devices.For example, enclosure 108 may include additional power supplies andsupport hardware that is not specific to UCS 100. In particular,enclosure 108 may also include one or more fabric extenders 162. In thisparticular embodiment, two fabric extenders 162-1 and 162-2 are shown.Fabric extenders 162 may be special UCS nodes that may occupy a blade orrack position within enclosure 108. In one embodiment, fabric extender162-1 and fabric extender 162-2 may be operable to service differenttypes of servers 110.

For example, fabric extender 162-1 may be configured and operableprimarily to service full-slot servers 110-1, while fabric extender162-2 may be configured and operable primarily to service half-slotserver 110-2. In certain embodiments, the primary intelligence forperforming UCS functions with an enclosure 108 is provided by fabricextenders 162. Thus, fabric extenders 162 may sit as an intermediarybetween servers 110 and a fabric interconnect 140. By way of example,fabric extender 162-1 may include adaptive firmware P, which may beoperable to perform global NIC configuration and perform statistics andhousekeeping. Fabric extender 162 may include a chassis manager C, whichis configured to perform server discovery and sequencing, powermanagement, temperature monitoring, and fan control looping. Aninterconnect infrastructure I may be included to provide a data routinginterface. In certain embodiments, each of P, I, and C may be providedas ASICs or other fixed-logic device. Advantageously, ASICs provideincreased processing speed and efficiency over certain programmableprocessing devices. It should be noted, however, that the specificfeatures of fabric extender 162-1 are provided by way of example only,and are intended to be nonlimiting. It will be recognized that manyadditional configurations are possible for a fabric extender 162, and itis intended that they be included within the scope of thisSpecification.

Fabric extender 162 may communicatively couple enclosure 108 to a one ormore fabric interconnects 140. In this example, two fabric interconnects140-1 and 140-2 are provided. In an example, fabric interconnect 140-1is configured and operable to communicate primarily with fabric extender162-1. Fabric interconnect 140-2 is configured and operable primarily tocommunicate and work with fabric extender 162-2. However, it will berecognized that many other configurations are possible.

Notably, each fabric interconnect 140-1 includes a UCSM 142. UCSMs 142may be operable to perform UCS configuration and control services withinthe context of UCS 100. Thus, the primary intelligence and top-levelcontrol of the overall UCS 100 is provided by UCSMs 142. UCSMs 142include, for example, infrastructure management subsystems,transactional information model subsystems, and an application gatewaysubsystem that may be configured to interact with system components. Inthis example, UCSM 142-1 of fabric interconnect 140-1 is communicativelycoupled to UCSM 142-2 of fabric interconnect 140-2. This provides, inone example, a completely redundant UCS fabric with two independentfabric interconnect paths.

Fabric interconnect may also include a plurality of application-specificintegrated circuits (ASICs) G, A, and S, provided for data pathconnectivity In this example, each UCSM 142 is communicatively coupledto a G ASIC. UCSMs 142 may also be communicatively coupled to cloudservices, such as management services 184. Fabric interconnect 140-1 and140-2 may also be configured to connect to other cloud services. Forexample, fabric interconnect 140-1 may communicatively couple to SAN180-1, while fabric connect fabric interconnect 140-2 may becommunicatively coupled to SAN 180-2.

Furthermore, fabric interconnect 140-1 and 140-2 may both jointlyconnect to a local area network (LAN) 182. Thus, UCS 100 is operable toconnect to a local network, and in appropriate instances may also beoperable to connect to a broader network such as an Internet. It shouldbe noted that LAN 182 and the Internet are provided by way of exampleonly, and other types of networks are anticipated herein. As usedherein, a network, including LAN 182, includes any communicativeplatform operable to exchange data or information within or betweencomputing devices, including by way of non-limiting example, an ad-hoclocal network, an internet architecture providing computing devices withthe ability to electronically interact, a plain old telephone system(POTS), which computing devices could use to perform transactions inwhich they may be assisted by human operators or in which they maymanually key data into a telephone or other suitable electronicequipment, any packet data network (PDN) offering a communicationsinterface or exchange between any two nodes in a system, or any localarea network (LAN), metropolitan area network (MAN), wide area network(WAN), wireless local area network (WLAN), virtual private network(VPN), intranet, or any other appropriate architecture or system thatfacilitates communications in a network or telephonic environment.

FIG. 2 is a block diagram of an intelligent platform managementinterface (IPMI) according to one or more examples of the presentSpecification. It should be noted that IPMI 200 is based around BMC 160,which was disclosed in FIG. 1. IPMI 200 is provided not as a replacementfor FIG. 1, but rather as an alternate view, in this case with focus onsignal interchange and IPMI functions. Thus, the hardware blocks of IPMI200 may, in certain embodiments, be realized within UCS 100. Those withskill in the art will recognize that there are many possible ways ofintegrating IPMI 200 into the disclosure of UCS 100.

IPMI is a standards-compliant system interface for computing platforms,and is useful, for example, in performing out-of-band management ofcomputing systems such as UCS 100. IPMI 200 may be operated by a systemadministrator in configuring access to computing resources.

For example, a customer may contact a system administrator and requestthat a virtual machine or hypervisor be configured with specificresources. The end user may request that the hypervisor have a specificUUID and a specific MAC address. In cases where adapter 170 is aUCS-aware adapter, this may be accomplished via out-of-band management.For example, the system administrator may use a standardized interfaceand protocols to perform management within UCS 100, which management mayinclude one or more servers 110. Advantageously, the IPMI system 200 ofFIG. 2 may be operated independent of OS 130 and bootstrap OS 136. Thus,IPMI 200 may be accessed and operated while one or more servers 110 arein a low-power state, such as standby state. IPMI 200 may alsoadvantageously be operated by a system administrator in the case that OS130 fails or becomes unreachable. This enables the system administratorto perform management of a server 110 without the need of interfacingwith a failed OS.

In an example, a system administrator uses IPMI messaging to performtasks such as monitoring the status of server 110, including parameterssuch as temperature, voltage, fans, power supplies, and chassisintrusion detection; query inventory information; review logs and alertcondition; and perform recovery procedures, including for exampleissuing requests for remote console access during system powered downand rebooting, or configuring watchdog timers. IPMI 200 may also includeprotocols for alerting the system administrator of special conditions.

In an example, IPMI 200 comprises a BMC 160. BMC 160 may also becommunicatively coupled, for example, to a Southbridge Super I/O 230, anadaptor 170, switching logic 250, and inter-integrated circuit (I2C)210. IPMI intelligence is provided by BMC 160. In certain embodiments,other controllers may be distributed among various subsystems of server110, within enclosure 108, or throughout UCS 100. These other managementcontrollers are treated herein as being logically connected to BMC 160,but it will be recognized, by those with skill in the art, that devicesmay be distributed in any suitable fashion, and that in some embodimentsBMC 160 may include more than one piece of physical hardware.

A system administrator may manage BMC 160 with the remote managementcontrol protocol (RMCP). In certain embodiments, where BMC 160 is to bemanaged over LAN 182 or over the Internet, an enhanced version of RMCPcalled RMCP+, which includes stronger authentication, may be used. BMC160 may include a specialized microcontroller, or other processorembedded within BMC 160, which itself may be embedded, for example,within a motherboard of server 110.

Physical interconnects to BMC 160 may include, by way of nonlimitingexample, a low-pin count (LPC) bus 270, system management bus (SMBUS)272, a serial bus 274, an I2C bus 278, and IPMI bus 276. In an example,each of these buses forms an interface to a class of connected devices.For example, IPMI bus 276 communicatively couples BMC 160 to IPMIdevices 220. I2C bus 278 communicatively couples BMC 160 to I2C devices210. LPC bus 270 communicatively couples BMC 160 to a Southbridge SuperI/O subsystem 230. SMBUS 272 communicatively couples BMC 160 to anetwork interface card (NIC) 240. Serial bus 274 communicatively couplesBMC 160 to switching logic 250, which is in turn communicatively coupledto a serial connector 252, which may be, for example, an RS-232, RS 422,Ethernet, FireWire, USB, or other suitable serial port, and to a superI/O 258.

In various embodiments, any or all of the peripheral devices describedin FIG. 2 may be either an in-band resource 134, or an out-of-bandresource 132.

For example, in one embodiment, LPC bus 270, and serial bus 274 may belegacy interfaces that are compatible only with legacy devices that arenot suitable for out of band management. On the other hand, IPMI bus276, I2C bus 278, and SMBUS 272 may all be more modern interfaces thatare suitable for out-of-band management by BMC 160. Thus, duringprovisioning of server 110, BMC 116 may appropriately provision NIC 240and I2C devices 210. IPMI devices 220 may be used in the provisioningstep to provide data to BMC 160. In other cases IPMI devices 220 mayalso need to be provisioned. Once BMC 160 has properly provisioned NIC240, IPMI devices 220, and 12C devices 210, out-of-band management iscomplete.

Server 110 may then disable IPMI bus 276, I2C bus 278, and SMBUS 272. Inmay then boot to bootstrap operating system 136, with only minimalprocessor 102 and memory 120 resources. Server 110 is then ready forprovisioning of in-band resources 134. Upon booting, bootstrap OS 136may discover the buses that are still enabled, namely LPC bus 270, andserial bus 274. Bootstrap OS 136 may then query LPC bus 270 and serialbus 274 for attached devices. Bootstrap OS 136 may therefore discoverSouthbridge super I/O 230, switching logic 250, super I/O 258, andserial connector 252. Finally, bootstrap OS 136 may perform in bandmanagement of these resources and provision them as necessary. Uponcompletion of this step, server 110 may be properly configured and readyfor use by an end user, and may be powered down, upon which persistentconfiguration of both in-band and out-of-band resources is maintained.

FIG. 3 is a functional block diagram of select elements of a server 110according to one or more examples of the present Specification. In thisexample, server 110 includes BMC 160, which may be communicativelycoupled to an I/O controller hub 330. BMC 160 may also becommunicatively coupled to UCSM 142. UCSM 142 is communicatively coupledto various client devices. These include a media client 380, akeyboard-video-mouse (KVM) client 382, a secure socket layer (SSL)client 384, and an IPMI client 386.

I/O controller hub 330 may be a subassembly of server 110, and in thisembodiment includes a basic input/output system (BIOS) 334, andbootstrap OS 136.

UCSM 142 includes a number of logical blocks, such as a DME 352, an IPtables/network address translation (NAT) module 362, a pluggableauthentication module (PAM) 358, a host aggregator 356, and a managementcontroller 354. UCSM 142 is also communicatively coupled to a UCS I/Omodule 360, which may be provided to manage input and output servicesfor UCSM 142. The functions of IP tables/NAT module 362, PAM 358, hostaggregator 356, and DME 352 are all well known, and in an embodiment ofthis Specification, it is intended that these modules perform theirknown functions. Management controller 354 may be provided with theparticular function of providing a communications interface to BMC 160.

BMC 160 also includes a number of logical blocks. For example, BMC 160may include a media server 318, a peripheral server 322, a serial server324, a serial proxy 326, and an IPMI server 390. In an example, thelogical blocks of BMC 160 may be provided for performing out-of-bandmanagement and configuring interfaces to a plurality of clients. Forexample, graphics controller 316 may configure a graphics device for usewith KVM client 382. Similarly, media server 318 may be operable forconfiguring services for media client 380. IPMI server 390 may provisionservices for IPMI client 386.

In addition to the logical blocks disclosed above, BMC 160 may include asuper I/O interface 314 for communicating with bootstrap OS 136 and BIOS334, and a processor 320. Processor 320 may include any combination ofhardware, software, or firmware providing programmable logic, includingby way of non-limiting example a microprocessor, DSP, FPGA, PLA, ASIC,or virtual machine processor.

In an embodiment, a front panel 350 may be provided as an interactiveinterface for an end-user to view the status of BMC 160 and to performlimited control functions. Sensors and component interface 340 may alsobe provided so that BMC 160 may interface with sensors and othercomponents.

It should be noted that FIG. 3 includes a number of logical blocks andelements, each of which is provided by way of nonlimiting example only.Each of the logical blocks of FIG. 3 may include, as appropriate, anycombination of hardware, software, and/or firmware necessary toimplement its function. Thus, it should be recognized that certainhardware, software, and firmware elements may be shared between variouslogical blocks, and the logical blocks may be understood to provide adivision of function more than a strict division of substance. Thosewith skill in the art will recognize that there are many additional waysto implement the devices shown in FIG. 3.

FIG. 4 is a block diagram of an example method 400 of performingdiscovery and configuration of a server 110 according to one or moreexamples of the present Specification. Method 400 starts in block 402.In block 410, UCSM 142 discovers out-of-band devices and resources onone or more servers 110. As described in this Specification, out-of-banddevices include devices that are configurable by a BMC 160, or that areotherwise UCS-aware. Discovery of out-of-band devices is accomplishedwithout needing to boot OS 130 or bootstrap OS 136.

In block 420, UCSM 142 configures out-of-band devices. In some examples,this configuration is persistent, and may be stored for example on aninternal flash memory for out-of-band devices. Thus, powering off server110 and/or rebooting server 110 does not affect configuration ofout-of-band devices.

In block 430, UCSM 142 sets up bootstrap OS 136. This may beaccomplished, for example, by sending an appropriate signal to full-slotserver 110 instructing server 110 to perform any actions necessary toprepare bootstrap OS 136 for operation. In block 440, server 110 bootsbootstrap OS 136. Booting bootstrap OS 136 may include a number ofsteps. For example, in one embodiment, bootstrap OS 136 performs a fullpower-on self-test (POST). The POST may include, for example, checkingeach individual cell of memory 120. It may also include performing otherself-test features, and scanning hardware. In some examples, each coreof processor 102 performs one or more self-test functions.

After the POST is complete, server 110 discovers all attached devices.Discovery of devices includes both out-of-band devices and in-banddevices. In some embodiments, discovery of devices may also includeperforming self-testing of devices or otherwise scanning the devices.

Once the devices are properly discovered, bootstrap OS 136 loadsappropriate drivers for each device. This may include for exampleloading kernel modules that are configured to handle each device. Itwill be recognized that in some cases, performing step 440 may take asubstantial time. In one example, step 440 may take approximately tenminutes or more. For some users and clients waiting for resources to beallocated, this delay may be unacceptable. In certain embodiments, thePOST is the most time-consuming single element of block 440. This isparticularly true where server 110 includes a large amount of memory120. In some cases, server 110 may include up to several terabytes ofmemory. Performing a POST of each cell of several terabytes of memory,as well as multiple cores of each of several processors 102, may be verytime-consuming.

In block 450, bootstrap OS 136 discovers all devices attached to server110. Notably, discovery of devices attached to server 110 includesdiscovery of both in-band devices and out-of-band devices. However, incertain cases, out-of-band devices may be ignored in step 450, becausethose out-of-band devices were discovered and configured persistently inblock 420. Thus, out-of-band devices may be ignored in block 450.

In block 460, bootstrap OS 136 configures discovered in-band devices. Aswith the configuration of out-of-band devices, configuration of in-banddevices in block 460 may be persistent.

In block 470, once discovery of all in-band devices is complete, andthose in-band devices have been properly and persistently configured,server 110 may shut down bootstrap OS 136.

In block 480, devices are properly detected, persistently configured,and allocated. Thus, server 110 is prepared to boot to a hypervisorenvironment for operation by a user. It should be recognized that ahypervisor environment is disclosed as only one example of a possibleconfiguration of server 110, and that many other configurations, such asa virtual machine, or native OS are possible for booting server 110.

In block 490, method 400 is complete.

FIG. 5 is a flow diagram of a method 500 of configuring allocatingresources according to one or more examples of the presentSpecification. Method 500 starts in block 502. In block 510, UCSM 142discovers out-of-band devices and resources on one or more servers 110.As described in this Specification, out-of-band devices include devicesthat are configurable by a BMC 160, or that are otherwise UCS-aware.Discovery of out-of-band devices is accomplished without needing to bootOS 130 or bootstrap OS 136.

In block 520, UCSM 142 configures out-of-band devices. In some examples,this configuration is persistent, and may be stored for example on aninternal flash memory for out-of-band devices. Thus, powering off server110 and/or rebooting server 110 does not affect configuration ofout-of-band devices.

In block 530, UCSM 142 sets up bootstrap OS 136. This may beaccomplished, for example, by sending an appropriate signal to full-slotserver 110 instructing server 110 to perform any actions necessary toprepare bootstrap OS 136 for operation.

In block 540, bootstrap OS 136 may disable out-of-band devices andexcess resources. Disabling out-of-band devices may include poweringthem down, or simply allocating a table that indicates that the devicesare not to be detected or configured in the following steps. In oneexample, disabling excess resources includes disabling all but one coreof each processor 102. Disabling excess resources may also includedisabling all but one memory bank of memory 120 for each processor 102.This provides a minimal amount of processing power and memory during theboot process. Although this processing power and memory may besubstantially reduced from the total available within server 110, thetrade-off may be acceptable inasmuch as bootstrap OS 136 is notconfigured to perform heavy processing loads, but rather to onlyconfigure in-band devices, and otherwise prepare server 110 foroperation by an end user.

In block 542, server 110 boots bootstrap OS 136. As with block 440 ofFIG. 4, booting bootstrap OS 136 may involve a POST. However, instead ofseveral terabytes of memory, this process may include a self-test ofonly a few gigabytes, or in some examples only a few hundred megabytesof memory. Furthermore, rather than involving multiple cores of multipleprocessors, the POST of block 542 involves only one core of severalprocessors in an example embodiment. As noted above, the POST of block440 of FIG. 4 may be the most time-consuming aspect of booting bootstrapOS 136. Thus, by disabling excess resources that are not necessary ordesirable for carrying out the function of bootstrap OS 136, block 542of FIG. 5 may substantially reduce the time to complete the booting ofbootstrap OS 136. As with block 440 of FIG. 4, block 542 discoversavailable devices and loads drivers for those devices. However, in oneembodiment, rather than scanning, discovering, and loading drivers forall attached devices to server 110, the scanning, discovering, andloading of block 542 involves only scanning, discovering, and loadingdrivers for in-band devices that were not disabled in block 540.

Thus, in block 550, discovery of devices involves discovering onlyremaining devices, which in an example includes only in-band devices andother devices minimally necessary to boot bootstrap OS 136.

In block 560, server 110 configures in-band devices. As with block 460of FIG. 4, this configuration is persistent, so that when bootstrap OS136 is shut down, and server 110 is powered down or restarted, theconfiguration is not lost.

In block 570, configuration and preparation is complete, so thatbootstrap OS 136 may be shut down.

In block 580, server 110 is properly prepared and provisioned, and ahypervisor is booted. As before, a hypervisor is disclosed as only oneexample of a possible operating configuration for server 110.

In block 590, method 500 is done.

Throughout this Specification, certain features of the disclosure may bedescribed in terms of modules, functions, or other logical blocks. Itshould be noted that according to modern computer architecturepractices, these logical blocks may include any combination of hardware,software, firmware, or similar. For example, any computing devicedisclosed herein may include a processor, a memory, and one or moreinterconnect interfaces. In many cases, however, a processor may beprovided as part of a virtual machine architecture or other emulation orvirtualization environment, in which a physical processor provides avirtual processor via software. Similarly, “memory” need not refer to asingle monolithic memory element or structure. Rather, “memory” mayinclude, by way of non-limiting example, on-chip cache, L1 memory, L2memory, cache memory, main memory, paging files, or virtual memory.Furthermore, a memory structure such as a main memory may be subdividedinto one or more memory banks, which may be interleaved or otherwisearranged.

Logical blocks also need not be physically separate devices. Forexample, in some cases, a “memory” and a “storage” will be shown asseparate logical blocks, but those with skill in the art will easilyrecognize that in some architectures, a single physical memory block mayserve as both a main memory and a storage region. Similarly, a networkinterface and a peripheral interface may be disclosed as separatelogical blocks, but in many cases, a network protocol such as a virtualterminal or hypervisor is provided so that peripherals and userinterface elements are accessed via a network such as an internetprotocol (IP) network.

Thus, at a high level, it should be appreciated that the logical blocksdisclosed herein represent functions that may be carried out by somecombination of hardware, software, and/or firmware, while the variousinterfaces disclosed represent any communication medium, includingappropriate hardware and software protocols, internal or external, thatmay be used to communicatively couple those logical elements to oneanother.

The foregoing outlines features of several embodiments so that thoseskilled in the art may better understand the aspects of the presentdisclosure. Those skilled in the art should appreciate that they mayreadily use the present disclosure as a basis for designing or modifyingother processes and structures for carrying out the same purposes and/orachieving the same advantages of the embodiments introduced herein.Those skilled in the art should also realize that such equivalentconstructions do not depart from the spirit and scope of the presentdisclosure, and that they may make various changes, substitutions, andalterations herein without departing from the spirit and scope of thepresent disclosure.

Certain embodiments, including for example BMC 160, may readily includea system on chip (SOC) central processing unit (CPU) package. An SOCrepresents an integrated circuit (IC) that integrates components of acomputer or other electronic system into a single chip. It may containdigital, analog, mixed-signal, and other functions: all of which may beprovided on a single chip substrate. Other embodiments may include amulti-chip-module (MCM), with a plurality of chips located within asingle electronic package and configured to interact closely with eachother through the electronic package. In various other embodiments, thedigital signal processing functionalities may be implemented in one ormore silicon cores in Application Specific Integrated Circuits (ASICs),Field Programmable Gate Arrays (FPGAs), and other semiconductor chips.

In example implementations, at least some portions of the processingactivities outlined herein may also be implemented in software. In someembodiments, one or more of these features may be implemented inhardware provided external to the elements of the disclosed figures, orconsolidated in any appropriate manner to achieve the intendedfunctionality. The various components may include software (orreciprocating software) that can coordinate in order to achieve theoperations as outlined herein. In still other embodiments, theseelements may include any suitable algorithms, hardware, software,components, modules, interfaces, or objects that facilitate theoperations thereof.

Additionally, some of the components associated with describedmicroprocessors may be removed, or otherwise consolidated. In a generalsense, the arrangements depicted in the figures may be more logical intheir representations, whereas a physical architecture may includevarious permutations, combinations, and/or hybrids of these elements. Itis imperative to note that countless possible design configurations canbe used to achieve the operational objectives outlined herein.Accordingly, the associated infrastructure has a myriad of substitutearrangements, design choices, device possibilities, hardwareconfigurations, software implementations, equipment options, etc.Furthermore, in various embodiments, the processors, memories, networkcards, buses, storage devices, related peripherals, and other hardwareelements described herein may be realized by a processor, memory, andother related devices configured by software or firmware to emulate orvirtualize the functions of those hardware elements.

Any suitably-configured processor component can execute any type ofinstructions associated with the data to achieve the operations detailedherein. Any processor disclosed herein could transform an element or anarticle (for example, data) from one state or thing to another state orthing. In another example, some activities outlined herein may beimplemented with fixed logic or programmable logic (for example,software and/or computer instructions executed by a processor) and theelements identified herein could be some type of a programmableprocessor, programmable digital logic (for example, (FPGA), an erasableprogrammable read only memory (EPROM), an electrically erasableprogrammable read only memory (EEPROM)), an ASIC that includes digitallogic, software, code, electronic instructions, flash memory, opticaldisks, CD-ROMs, DVD ROMs, magnetic or optical cards, other types ofmachine-readable mediums suitable for storing electronic instructions,or any suitable combination thereof. In operation, processors may storeinformation in any suitable type of non-transitory storage medium (forexample, random access memory (RAM), read only memory (ROM), (FPGA),(EPROM), (EEPROM), etc., software, hardware, or in any other suitablecomponent, device, element, or object where appropriate and based onparticular needs. Further, the information being tracked, sent,received, or stored in a processor could be provided in any database,register, table, cache, queue, control list, or storage structure, basedon particular needs and implementations, all of which could bereferenced in any suitable timeframe. Any of the memory items discussedherein should be construed as being encompassed within the broad term‘memory.’ Similarly, any of the potential processing elements, modules,and machines described herein should be construed as being encompassedwithin the broad term ‘microprocessor’ or ‘processor.’

Computer program logic implementing all or part of the functionalitydescribed herein is embodied in various forms, including, but in no waylimited to, a source code form, a computer executable form, and variousintermediate forms (for example, forms generated by an assembler,compiler, linker, or locator). In an example, source code includes aseries of computer program instructions implemented in variousprogramming languages, such as an object code, an assembly language, ora high-level language such as OpenCL, Fortran, C, C++, JAVA, or HTML foruse with various OSs or operating environments. The source code maydefine and use various data structures and communication messages. Thesource code may be in a computer executable form (e.g., via aninterpreter), or the source code may be converted (e.g., via atranslator, assembler, or compiler) into a computer executable form.

In the discussions of the embodiments above, the buffers, graphicselements, interconnect boards, clocks, DDRs, switches, digital core,transistors, and/or other components can readily be replaced,substituted, or otherwise modified in order to accommodate particularcircuitry needs. Moreover, it should be noted that the use ofcomplementary electronic devices, hardware, non-transitory software,etc. offer an equally viable option for implementing the teachings ofthe present disclosure.

In one example embodiment, any number of electrical circuits of theFIGURES may be implemented on a board of an associated electronicdevice. The board can be a general circuit board that can hold variouscomponents of the internal electronic system of the electronic deviceand, further, provide connectors for other peripherals. Morespecifically, the board can provide the electrical connections by whichthe other components of the system can communicate electrically. Anysuitable processors (inclusive of digital signal processors,microprocessors, supporting chipsets, etc.), memory elements, etc. canbe suitably coupled to the board based on particular configurationneeds, processing demands, computer designs, etc. Other components suchas external storage, additional sensors, controllers for audio/videodisplay, and peripheral devices may be attached to the board as plug-incards, via cables, or integrated into the board itself. In anotherexample embodiment, the electrical circuits of the FIGURES may beimplemented as stand-alone modules (e.g., a device with associatedcomponents and circuitry configured to perform a specific application orfunction) or implemented as plug-in modules into application specifichardware of electronic devices.

Note that with the numerous examples provided herein, interaction may bedescribed in terms of two, three, four, or more electrical components.However, this has been done for purposes of clarity and example only. Itshould be appreciated that the system can be consolidated in anysuitable manner. Along similar design alternatives, any of theillustrated components, modules, and elements of the FIGURES may becombined in various possible configurations, all of which are clearlywithin the broad scope of this Specification. In certain cases, it maybe easier to describe one or more of the functionalities of a given setof flows by only referencing a limited number of electrical elements. Itshould be appreciated that the electrical circuits of the FIGURES andits teachings are readily scalable and can accommodate a large number ofcomponents, as well as more complicated/sophisticated arrangements andconfigurations. Accordingly, the examples provided should not limit thescope or inhibit the broad teachings of the electrical circuits aspotentially applied to a myriad of other architectures.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “steps for” are specifically used in theparticular claims; and (b) does not intend, by any statement in theSpecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

What is claimed is:
 1. A management controller configured forprovisioning of resources comprising: a processor; a network interfaceoperable to communicatively couple the processor to a baseboardmanagement controller (BMC) resident on a server; and a memorycommunicatively coupled to the processor and operable to instruct theprocessor for provisioning, comprising: communicating with the BMC toidentify an out-of-band resource available on the server in a low-powerstate; determining a minimally sufficient hardware configuration with aminimal amount of processing power and memory to persistently configurean in-band resource, wherein the in-band resource is determined not tobe configurable by the resident BMC via a discovery process; disablingthe out-of-band resource and at least one additional resource on theserver based on the minimally sufficient hardware configuration; bootingthe server to an OS in a higher-power state; communicating with the OSto identify the in-band resource on the server; and communicating withthe OS to persistently configure the in-band resource.
 2. The managementcontroller of claim 1, wherein disabling at least one additionalresource comprises disabling at least one processor core.
 3. Themanagement controller of claim 1, wherein disabling at least oneadditional resource comprises disabling all but one core of each of aplurality of processors.
 4. The management controller of claim 1,wherein the OS is a bootstrap OS.
 5. The management controller of claim4, wherein disabling at least one additional resource comprisesdisabling all out-of-band resources not included in theminimally-sufficient hardware configuration.
 6. The managementcontroller of claim 1, further comprising: a management system coupledto a plurality of client servers, wherein the management system isconfigured to provision the plurality of client servers.
 7. One or morenon-transient computer-readable mediums having stored thereoninstructions operable to instruct a processor for provisioning,comprising: communicating with a baseboard management controller (BMC)to identify an out-of-band resource available on a server in a low-powerstate; determining a minimally sufficient hardware configuration with aminimal amount of processing power and memory to persistently configurean in-band resource, wherein the in-band resource is determined not tobe configurable by the resident BMC via a discovery process; disablingthe out-of-band resource and at least one additional resource on theserver based on the minimally sufficient hardware configuration; bootingthe server to an OS in a higher-power state; communicating with the OSto identify the in-band resource on the server; and communicating withthe OS to persistently configure the in-band resource.
 8. The one ormore non-transient computer-readable mediums of claim 7, whereindisabling at least at least one additional resource comprises disablingat least one processor core.
 9. The one or more non-transientcomputer-readable mediums of claim 7, wherein disabling at least oneadditional resource comprises disabling all but one core of each of aplurality of processors.
 10. The one or more non-transientcomputer-readable mediums of claim 7, wherein the OS is a bootstrap OS.11. The one or more non-transient computer-readable mediums of claim 10,wherein disabling at least one additional resource comprises disablingall out-of-band resources not necessary to operate the bootstrap OS. 12.A method of provisioning resources performed by a computing devicecomprising: communicating with a baseboard management controller (BMC)to identify an out-of-band resource available on a server in a low-powerstate; determining a minimally sufficient hardware configuration with aminimal amount of processing power and memory to persistently configurean in-band resource, wherein the in-band resource is determined not tobe configurable by the resident BMC via a discovery process; disablingthe out-of-band resource and at least one additional resource on theserver based on the minimally sufficient hardware configuration; bootingthe server to an OS in a higher-power state; communicating with the OSto identify the in-band resource on the server; and communicating withthe OS to persistently configure the in-band resource.
 13. The method ofclaim 12, wherein disabling at least at least one additional resourcecomprises disabling at least one processor core.
 14. The method of claim12, wherein disabling at least one additional resource comprisesdisabling all but one core of each of a plurality of processors.
 15. Themethod of claim 12, wherein the OS is a bootstrap OS.
 16. The method ofclaim 15, wherein disabling at least one additional resource comprisesdisabling all out-of-band resources not necessary to operate thebootstrap OS.
 17. The method of claim 12, further comprising: performingat least one memory blacklisting process to disable a plurality ofmemory devices per a central processing unit (CPU).
 18. The managementcontroller of claim 4, wherein disabling at least one additionalresource comprises disabling all resources not necessary to operate thebootstrap OS.
 19. The one or more non-transient computer-readablemediums of claim 7, wherein the instructions are further to instruct theprocessor to reboot the server into an operational operating system. 20.The method of claim 12, further comprising rebooting the server into anoperational operating system.